home *** CD-ROM | disk | FTP | other *** search
- Path: airdmhor.gen.nz!not-for-mail
- From: gumboot@airdmhor.gen.nz (Simon Hosie)
- Newsgroups: comp.lang.c
- Subject: Re: Using own stacks with borlandc
- Date: 3 Feb 1996 06:45:48 +1300
- Organization: Airdmhor
- Message-ID: <4etikc$fbq@airdmhor.gen.nz>
- References: <4ef339$24q@thor.atcon.com> <4eisl3$9d2@airdmhor.gen.nz> <4elvir$ood@news.bellglobal.com>
- NNTP-Posting-Host: localhost.gen.nz
- X-Newsreader: TIN [version 1.2 PL2]
-
- Simon Hosie:
- > Turn off stack overflow checking for a start.. umm.. you can assume ds=ss
- > if your own stack is near (ie. short near Stack[1024]). If you don't use
- > near in the declaration (or if you don't use nmalloc()) then turn it off.
-
- Steve Tupy:
- > Ouch! You would endanger the whole stack checking mechanism in lieu
- > of altering the stack size? It is easy to turn it off via pragmas whenever
- > you need to without depriving your whole program of this rather handy
- > feature, don't you agree?
-
- You have to know _every_ function that will be executed while you're using
- your alterntive stack, though.
-
- When is the stack actually checked, anyway? On entry/exit of functions
- only?
-